Product design
38 bites tagged Product design: interview questions with model answers, and 60-second explainers.
Test yourself: Top 30 Product design interview questions →Multiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.UX Data Storytelling That Drives Decisions
Raw metrics fail to move teams; stakeholders cannot feel user pain. Storytelling with data weaves findings into a narrative arc exposing friction and driving action. The footgun is cherry-picking to fit a preset conclusion instead of letting data lead.
UX Research Report: Decisions, Not Deliverables
A UX research report is a decision tool, not a data dump; it turns observations into product direction. Teams use it after usability tests to align stakeholders on what to build. The biggest mistake is writing for your ego instead of the reader's next move.
Usability Benchmarking: Quantifying Product Friction
Usability benchmarking is a fitness tracker for your product: you measure task success against a baseline or competitor to prove changes reduce friction. Use it to justify redesigns, but the footgun is testing too few users and mistaking noise for trend.
UX Research Plan: Alignment Before Fieldwork
A UX research plan is a pre-fieldwork contract that locks in what you must learn and how success is judged. It stops stakeholders from moving goalposts after interviews begin. The footgun is filing it away unread; a plan nobody references is just bureaucracy.
Lean UX: Outcomes Over Deliverables
Lean UX treats design as a hypothesis, not a specification. Cross-functional teams run minimum viable experiments, gather user feedback early, and iterate. The footgun: obsessing over polished deliverables instead of validated learning.
Research Advocacy in UX Design
Research advocacy means suspending your own priorities to speak with the user's voice in product decisions. It matters when teams must translate raw user frustration into concrete design changes. The footgun is letting personal opinion masquerade as user need.
UX Competitive Analysis: Benchmark to Outperform
UX competitive analysis treats rivals as free design research: reverse-engineer what works and where the market is underserved. Run it before redesigns and repeat quarterly. The footgun is copying visuals instead of analyzing underlying flows and task success.
RITE Method: Rapid Iterative Testing and Evaluation
RITE treats usability as a rapid feedback loop: test, evaluate, iterate. Championed in Microsoft game development, it suits teams shipping interactive products fast.
Shopify's 0% to 100% Fix: Design Dialects Over Rigidity
Shopify Polaris hit 0% completion for gloved warehouse pickers until a dialect with 90px targets and dark UI hit 100%, cutting onboarding from three weeks to one shift. Atlassian formalized this into a three-tier Flexibility Framework. Rigid systems break.
First Figma steps to turn a brief into low-fi concepts
This tests whether you structure IA before pixels. Strong answers audit the brief, map flows with simple frames, block out grayscale wireframes at target breakpoints, and annotate for async review. Red flag: jumping straight to components or color.
Voice and Tone: One Voice, Many Moods
Voice is your product's personality; tone is its mood in the moment. Guidelines keep every button and error message from feeling written by different teams. The footgun is documenting voice but skipping tone, so a cheerful brand still sends terrifying alerts.
Task Analysis: Mapping User Goals to Actions
Task analysis maps the specific actions (tasks) a user takes to achieve their larger objective (goal). It's used to ensure a product actually helps users, not just creates busywork. The key mistake is designing for the task instead of the user's true goal.
Think Aloud Protocol: Hear Your User's Inner Monologue
See your product through a user's eyes by having them narrate their thoughts live during a task. It's used in usability testing to uncover confusion, mismatched expectations, and the "why" behind clicks.
Participatory Design: Designing With, Not For, Users
Participatory design means designing *with* users as co-creators, not just *for* them. It's used in software, architecture, and urban planning to ensure the final product truly fits the community.
Double Diamond: Explore, Then Focus, Twice
The Double Diamond model prevents building the wrong thing by forcing two cycles of 'go wide, then narrow down.' First, explore the problem space, then define a specific problem. Second, explore solutions, then deliver a tested one.
User Flow Diagrams: Mapping the Path to 'Done'
A user flow diagram maps the exact steps a user takes in your app to complete one task. It aligns teams on product goals and gives developers a visual guide, preventing confusion and rework. The footgun: it's not a customer journey, which is far broader.
Drive Design System Adoption, Don't Just Build It
Treat your design system like an internal product, not a one-off project. To drive adoption, show quick, measurable wins and offer tiered onboarding for different roles.
The Design Critique: Improving Work with Focused Feedback
A design critique is a structured conversation to measure a design against its goals, not a session for subjective opinions. It helps get early feedback on feasibility or catch inconsistencies.
Usability Testing: Watch Real Users, Not Just Experts
Usability testing evaluates a product by observing real, first-time users interact with it, revealing flaws that designers often miss. It's used to validate design intuitiveness before launch.
Iterative Design: Build, Test, Learn, Repeat
Iterative design is a cycle of building, testing, and refining based on user feedback. It's standard for app development, where you ship a basic version and improve it with data. The footgun is mistaking any change for iteration; it requires real user testing.
Information Architecture: The Blueprint for Your App
Think of Information Architecture (IA) as the blueprint for an app, defining its structure before visual design begins. It dictates navigation and content organization to make things findable.
User-Centered Design: Build for Who, Not What
User-Centered Design (UCD) puts the user's goals, tasks, and environment at the core of development. This process shapes software and websites through user personas and real-world testing.
Streaks: Engineering Identity Through Loss Aversion
Streaks convert effort into identity, making users fear losing progress more than they enjoy extending it. Apps like Duolingo use this for daily engagement, but the footgun is when the streak itself becomes the goal, trapping users in a loop of loss aversion.
Onboarding Gamification: Guiding Users with Game Mechanics
Onboarding gamification uses game-like elements to guide new users through key actions, turning a checklist into a challenge. It's used to boost activation by making initial setup feel rewarding, like earning a badge for completing your profile.
Get Product design bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.